CommentRe: Why one week only? (Score 1)16
I think ours started showing this in October. Maybe it is for the non science museum theaters?
I think ours started showing this in October. Maybe it is for the non science museum theaters?
This was even weirder because I have parental controls on my sonâ(TM)s computer, and I got an email out of nowhere that he had bought HP Smart for $0.
Ah yes, less than absolute zero. That is cold.
They aren't charging enough on fares to keep their company and the drivers running. They've tried to become more sustainable by trimming driver payments, but it's still not enough. Even with a limited monopoly, taxi companies weren't incredible profit generators. The main reason Uber and Lyft are cheaper is that they're being subsidized by investors to try to get enough of a market dominance they can then increase prices.
I havenâ(TM)t read details about the WhatsApp hack but what I have read is that it only impacted that app, not other apps or system processes. So the sand boxing may have helped mitigate the damage.
Or laser, or NASA.
Well, apparently you can get away with this in New York, New Mexico, and lots of other places.
It was in the summary. The keyboard in question is AI.type.
Neither can Tesla, right now. Tesla is promising full autonomous driving, but it isn't there yet. It also has lost features from the original AP1 hardware (reliable automatic windshield wipers) that it has not yet replicated with AP2, because it's relying on different hardware and software to enable it.
Tesla is really betting on "software will fix everything", but there's really no saying when it'll happen.
How likely is it that they will catch the people who did it? And if they do, how likely is that to reduce the chances of someone else doing the same thing?
If someone steals your car, you contact the cops because it's possible you'll get your car back. Even if not, it's sort of possible they'll find the car thief, because the city is only so big. But finding who put ransomware on your computer among billions of people all over the world?
Again, there's nothing in it for the victim.
Law enforcement isn't going to do anything to help you about ransomware hitting your computer. For the victim, it's a waste of time.
I will be honest, wired syncing isnâ(TM)t much of a thing anymore for a lot of people. I havenâ(TM)t synced this phone with iTunes at all since I got it. Everything is over wireless including backups.
The demo video is definitely web-based. Possibly within a shell like Cordova to get into the App Store.
Or, would an HP printer of today outperform theirs from the 90s?
The Accidental Tech Podcast had an interview with Chris Lattner where he discussed the future of Swift as a systems language and compared it to Rust. Rust has a very upfront memory ownership model that requires programmers to be explicit about memory management. This allows Rust to have great performance and allows the compiler to ensure memory is used safely that is not an option with C.
With Swift, either you pretty much don't think about memory (it uses Automatic Reference Counting so you only need to care about cycles), or you need to go down to C-style memory semantics with the various Unsafe constructions. There are cases where you could get much better performance because the programmer knows the lifecycle of the objects being used, but that can't currently be expressed in Swift. It can be expressed in Rust.
To be a good systems programming language, Chris said that Swift will need to create a memory ownership model (and mentioned Rust as having ideas that might apply). He would like that ownership model to be opt-in for specific pieces of your code that require it: most people could use ARC, while people that need performance in a specific piece could be more detailed about the memory management. It's on his list of things that Swift will acquire over the years so it can achieve world domination.
So there are really pretty good reasons that Mozilla put together Rust. The browser is probably the most widely exposed attack surface right now, and the history of buffer overloads means there needed to be a safer way to code.
"We live, in a very kooky time." -- Herb Blashtfalt